home *** CD-ROM | disk | FTP | other *** search
/ IRIX Base Documentation 2002 November / SGI IRIX Base Documentation 2002 November.iso / usr / share / catman / g_man / cat3 / OpenGL / glxcreatenewcontext.z / glxcreatenewcontext
Encoding:
Text File  |  2002-10-03  |  7.8 KB  |  133 lines
  1.  
  2.  
  3.  
  4. ggggllllXXXXCCCCrrrreeeeaaaatttteeeeNNNNeeeewwwwCCCCoooonnnntttteeeexxxxtttt((((3333GGGG))))     OOOOppppeeeennnnGGGGLLLL RRRReeeeffffeeeerrrreeeennnncccceeee ---- GGGGLLLLXXXX     ggggllllXXXXCCCCrrrreeeeaaaatttteeeeNNNNeeeewwwwCCCCoooonnnntttteeeexxxxtttt((((3333GGGG))))
  5.  
  6.  
  7.  
  8. NNNNAAAAMMMMEEEE
  9.      ggggllllXXXXCCCCrrrreeeeaaaatttteeeeNNNNeeeewwwwCCCCoooonnnntttteeeexxxxtttt - create a new GLX rendering context
  10.  
  11.  
  12. CCCC SSSSPPPPEEEECCCCIIIIFFFFIIIICCCCAAAATTTTIIIIOOOONNNN
  13.      GLXContext ggggllllXXXXCCCCrrrreeeeaaaatttteeeeNNNNeeeewwwwCCCCoooonnnntttteeeexxxxtttt( Display *_d_p_y,
  14.                                       GLXFBConfig _c_o_n_f_i_g,
  15.                                      int _r_e_n_d_e_r__t_y_p_e,
  16.                                      GLXContext _s_h_a_r_e__l_i_s_t,
  17.                                      Bool _d_i_r_e_c_t )
  18.  
  19.  
  20. PPPPAAAARRRRAAAAMMMMEEEETTTTEEEERRRRSSSS
  21.      _d_p_y          Specifies the connection to the X server.
  22.  
  23.      _c_o_n_f_i_g       Specifies the GLXFBConfig structure with the desired
  24.                   attributes for the context.
  25.  
  26.      _r_e_n_d_e_r__t_y_p_e  Specifies the type of the context to be created.  Must be
  27.                   one of GGGGLLLLXXXX____RRRRGGGGBBBBAAAA____TTTTYYYYPPPPEEEE or GGGGLLLLXXXX____CCCCOOOOLLLLOOOORRRR____IIIINNNNDDDDEEEEXXXX____TTTTYYYYPPPPEEEE.
  28.  
  29.      _s_h_a_r_e__l_i_s_t   Specifies the context with which to share display lists.
  30.                   NNNNUUUULLLLLLLL indicates that no sharing is to take place.
  31.  
  32.      _s_h_a_r_e__l_i_s_t   Specifies whether rendering is to be done with a direct
  33.                   connection to the graphics system if possible (TTTTrrrruuuueeee) or
  34.                   through the X server (FFFFaaaallllsssseeee).
  35.  
  36. DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
  37.      ggggllllXXXXCCCCrrrreeeeaaaatttteeeeNNNNeeeewwwwCCCCoooonnnntttteeeexxxxtttt creates a GLX rendering context and returns its
  38.      handle.  This context can be used to render into GLX windows, pixmaps, or
  39.      pixel buffers.  If ggggllllXXXXCCCCrrrreeeeaaaatttteeeeNNNNeeeewwwwCCCCoooonnnntttteeeexxxxtttt fails to create a rendering
  40.      context, NNNNUUUULLLLLLLL is returned.
  41.  
  42.      If _r_e_n_d_e_r__t_y_p_e is GGGGLLLLXXXX____RRRRGGGGBBBBAAAA____TTTTYYYYPPPPEEEE, then a context that supports RGBA
  43.      rendering is created.  If _c_o_n_f_i_g is GGGGLLLLXXXX____CCCCOOOOLLLLOOOORRRR____IIIINNNNDDDDEEEEXXXX____TTTTYYYYPPPPEEEE, then context
  44.      supporting color-index rendering is created.
  45.  
  46.      If _r_e_n_d_e_r__t_y_p_e is not NNNNUUUULLLLLLLL, then all display-list indexes and definitions
  47.      are shared by context _r_e_n_d_e_r__t_y_p_e and by the newly created context.  An
  48.      arbitrary number of contexts can share a single display-list space.
  49.      However, all rendering contexts that share a single display-list space
  50.      must themselves exist in the same address space.  Two rendering contexts
  51.      share an address space if both are nondirect using the same server, or if
  52.      both are direct and owned by a single process.  Note that in the
  53.      nondirect case, it is not necessary for the calling threads to share an
  54.      address space, only for their related rendering contexts to share an
  55.      address space.
  56.  
  57.      If _s_h_a_r_e__l_i_s_t is TTTTrrrruuuueeee, then a direct rendering context is created if the
  58.      implementation supports direct rendering, if the connection is to an X
  59.      server that is local, and if a direct rendering context is available. (An
  60.  
  61.  
  62.  
  63.                                                                         PPPPaaaaggggeeee 1111
  64.  
  65.  
  66.  
  67.  
  68.  
  69.  
  70. ggggllllXXXXCCCCrrrreeeeaaaatttteeeeNNNNeeeewwwwCCCCoooonnnntttteeeexxxxtttt((((3333GGGG))))     OOOOppppeeeennnnGGGGLLLL RRRReeeeffffeeeerrrreeeennnncccceeee ---- GGGGLLLLXXXX     ggggllllXXXXCCCCrrrreeeeaaaatttteeeeNNNNeeeewwwwCCCCoooonnnntttteeeexxxxtttt((((3333GGGG))))
  71.  
  72.  
  73.  
  74.      implementation may return an indirect context when _s_h_a_r_e__l_i_s_t is TTTTrrrruuuueeee.)
  75.      If _s_h_a_r_e__l_i_s_t is FFFFaaaallllsssseeee, then a rendering context that renders through the
  76.      X server is always created.  Direct rendering provides a performance
  77.      advantage in some implementations.  However, direct rendering contexts
  78.      cannot be shared outside a single process, and they may be unable to
  79.      render to GLX pixmaps.
  80.  
  81. NNNNOOOOTTTTEEEESSSS
  82.      ggggllllXXXXCCCCrrrreeeeaaaatttteeeeNNNNeeeewwwwCCCCoooonnnntttteeeexxxxtttt is available only if the GLX version is 1.3 or
  83.      greater.
  84.  
  85.      If the GLX version is 1.1 or 1.0, the GL version must be 1.0.  If the GLX
  86.      version is 1.2, then the GL version must be 1.1.  If the GLX version is
  87.      1.3, then the GL version must be 1.2.
  88.  
  89. EEEERRRRRRRROOOORRRRSSSS
  90.      NNNNUUUULLLLLLLL is returned if execution fails on the client side.
  91.  
  92.      GGGGLLLLXXXXBBBBaaaaddddCCCCoooonnnntttteeeexxxxtttt is generated if _r_e_n_d_e_r__t_y_p_e is not a GLX context and is not
  93.      NNNNUUUULLLLLLLL.
  94.  
  95.      GGGGLLLLXXXXBBBBaaaaddddFFFFBBBBCCCCoooonnnnffffiiiigggg is generated if _c_o_n_f_i_g is not a valid GLXFBConfig.
  96.  
  97.      BBBBaaaaddddMMMMaaaattttcccchhhh is generated if the context to be created would not share the
  98.      address space or the screen of the context specified by _r_e_n_d_e_r__t_y_p_e.
  99.  
  100.      BBBBaaaaddddAAAAlllllllloooocccc is generated if the server does not have enough resources to
  101.      allocate the new context.
  102.  
  103.      BBBBaaaaddddVVVVaaaalllluuuueeee is generated if _c_o_n_f_i_g is not a valid visual (for example, if a
  104.      particular GLX implementation does not support it).
  105.  
  106.  
  107. SSSSEEEEEEEE AAAALLLLSSSSOOOO
  108.      ggggllllXXXXCCCChhhhoooooooosssseeeeFFFFBBBBCCCCoooonnnnffffiiiigggg, ggggllllXXXXCCCCrrrreeeeaaaatttteeeeCCCCoooonnnntttteeeexxxxtttt, ggggllllXXXXDDDDeeeessssttttrrrrooooyyyyCCCCoooonnnntttteeeexxxxtttt, ggggllllXXXXGGGGeeeettttFFFFBBBBCCCCoooonnnnffffiiiiggggssss,
  109.      ggggllllXXXXGGGGeeeettttFFFFBBBBCCCCoooonnnnffffiiiiggggAAAAttttttttrrrriiiibbbb, ggggllllXXXXIIIIssssDDDDiiiirrrreeeecccctttt, ggggllllXXXXMMMMaaaakkkkeeeeCCCCoooonnnntttteeeexxxxttttCCCCuuuurrrrrrrreeeennnntttt
  110.  
  111.  
  112.  
  113.  
  114.  
  115.  
  116.  
  117.  
  118.  
  119.  
  120.  
  121.  
  122.  
  123.  
  124.  
  125.  
  126.  
  127.  
  128.  
  129.                                                                         PPPPaaaaggggeeee 2222
  130.  
  131.  
  132.  
  133.